Automated drone systems

ABSTRACT

An automated drone security system for surveilling a location includes one or more drones with onboard sensors and an imaging device for measuring surveillance data. The surveillance data may include images, telemetry data, infrared data, or other detectable information of the location. Drones may be capable of executing one or multiple flight operations as well as storing and transmitting the surveillance data to a server assembly operable for coordinating the drone and receiving the surveillance data. A drone dock may be included for drone launching, landing, and/or storing the drones. A user computing device may be in communication with the server assembly and the drone(s), the user computing device being capable of receiving user input and displaying surveillance data from the drone. Flight operations associated with surveilling the location may be automatically and/or manually controlled by the user computing device and/or or the server assembly in connection with the location.

CROSS-REFERENCE TO RELATED APPLICATION

This Application claims priority to and benefit under 35 U.S.C. §119(e)of U.S. Provisional Patent Application Ser. No. 62/132,311, filed Mar.12, 2015 which is hereby incorporated by reference in its entirety as iffully set forth below.

FIELD

The present disclosure generally relates to the security systems forunmanned air vehicles such as recreational drones.

BACKGROUND

Security systems known are subject to cumbersome installation ofconstituent parts and associated static location of imagine devices(e.g. cameras) that are installed therein. Because the cameras arestatic and difficult to install, dark spots can be exploited byintruders. Additionally, it has been proposed to send recorded and/orstreaming images to computing devices or portable computing devices suchthat the user of a smartphone can view information such as recordedimages (or images being recorded) or messages. In this respect, portablecomputing devices such as smart phones or tablets have been used forstoring, analyzing, and transmitting such information.

However, in order for any settings in a particular system to bemanipulated (i.e. to view different cameras, move the location of acamera, or any other administrative function), an end user typically hasto be near the location of the camera and/or be situated where theactual surveillance systems are located in order to make such changespermissible. It is with respect to these and other considerations thatthe various embodiments described below are presented.

SUMMARY

Embodiments of the present disclosure include an automated dronesecurity system security system for surveilling a location is disclosed,the system including a drone comprising one or more onboard sensors andan imaging device for measuring surveillance data. The surveillance datamay include images, telemetry data, infrared data, or other detectableinformation of the location to identify one or more changes associatedwith a particular event (e.g. a theft, a burglary, a break-in, anaccident, etc.), wherein the location may be understood as structure(s),building(s), parcel(s) of land, street(s), and/or the like. The dronemay be capable of executing one or multiple flight operations for aperiod of time as well as storing and transmitting the surveillance datato a server assembly. The server assembly of the system in turn may beoperable for coordinating the drone and receiving the surveillance data.A drone dock may also be included in the system for drone launching,landing, and/or storing the drone. A user computing device may also beincluded in the system and in communication with the server assembly andthe drone, the user computing device having a non-transitory storagemedium, a processor for processing data (including the surveillancedata) between the server assembly and the drone, and a user interfacefor receiving user input and displaying data transmitted from the drone.Flight operations associated with surveilling the location may beautomatically and/or manually controlled by the user computing device orthe server assembly in connection with the location.

In certain embodiments, a battery of the drone may be charged by thedrone dock through a conduction pad and/or through an inductive chargingdevice. In certain embodiments, when the battery of the drone has aminimum charge, the drone may be automatically returned to the dronedock for charging. In this respect, the system may also include flightand security control logic comprising one or more of the followingprocesses: executive logic defined by one or more predefined flight andoperation procedures triggered by sensor states associated with the oneor more onboard sensors of the drone including velocity, a timer, aninertial measurement unit, and/or a global positioning system (GPS);flight range prediction logic defined by a status of the battery of thedrone and environmental conditions including wind speed and direction,humidity, altitude, temperature, and air pressure, and a flighttrajectory planner associated with one or more flight operations; andautonomous logic associated with the flight range prediction logicincluding collision avoidance logic and control and encryption forinformation transmitted between the drone, the server assembly and theuser computing device.

In certain embodiments, the collision avoidance logic may include adetect and track module associated with static and dynamic structuresand obstacles defined by a predetermined location of the location beingsurveilled, a predetermined flight path, and/or static and dynamicstructures and obstacles sensed by the onboard sensors of the drone.

The system may also include a video feed system comprising one or moreof the following processes: stream quarter video graphics array (QVGA)video from an onboard computing system of the drone to a cloud serverassociated with the server assembly with a predetermined latency; relayQVGA video from the cloud server to the user computing device with asimilar predetermined latency; and stream or upload video in apredetermined format from the onboard computing system of the drone tothe cloud server, wherein the predetermined format is determined pendingnetwork bandwidth and encryption.

In other embodiments, the system may also include one or more additionaldrones and associated onboard computing systems with flight and securitycontrol logic, imaging devices, onboard sensors and associated sensorstates. The user computing device or the server assembly may alsopartially or automatically manage a flight operation for surveilling thelocation associated with each of the one or more additional drones forcontinuous, uninterrupted, and/or dynamic aerial coverage of thelocation being surveilled.

In other embodiments, the system may also include a process for formingor monitoring a continuously-updated two-dimensional and/orthree-dimensional map of the location with image stitching logic definedby two- and/or three-dimensional blending of previously and liverecorded two- and/or three-dimension data gathered from the one or moreonboard sensors and imaging devices of each drone. Further, one or moreof the drones of the system may maintain connectivity with the serverassembly or the user computing device through 3G/4G, RF, and/or a localwireless network.

In other embodiments, wherein one or more of the drones and/or the usercomputing device may be automatically configured based on data detectedfrom onboard sensors of the one or more drones. Alert messages of thisembodiment may also be automatically configured based on one or morepredetermined detected parameters of the location being surveilled orone or more of the drones surveilling the location. In this respect,alert messages can be caused to be manually or automatically transmittedto the user computing device or other user computing devices securelyconnected therewith so that end-users can quickly and reliably detectthat an event of interest may be occurring at the location.

The system may also include a plurality of drone docks positioned on orthroughout the location, wherein each drone can be capable of beinghoused, landing upon, and/or receiving a charge to its battery inconnection with any one of the plurality of drone docks. Each drone dockmay also be wirelessly connectable to the server assembly and/or theuser computing device to store and transmit data from one or more of thedrones docked thereon.

In other embodiments, the user computing device may include an eventscheduling manager for manually or automatically selecting one of thedrones to execute one of a plurality of flight operations. Flightoperations may include surveilling a specified structure of interest,surveilling a perimeter, surveilling a pattern across the entirety of ora portion of the location being surveilled, surveilling the location fora duration of time at a specified altitude, or any other operationconsistent with providing dynamic yet accurate aerial surveillancecoverage.

The user computing device of the system may also include an event viewerfor live viewing the flight operation being executed by drones of thesystem and/or for viewing previously captured data by drones of thesystem. The user interface may also display operational status of thedrone.

The server assembly may include a database server operatively connectedto one or more web servers across one or more networks, each serveroperable to permanently store and/or continuously update a database ofmaster surveillance data, telemetry information, mission data, collisionmapping, drone coordination, air traffic control, captured images, andvideo streams. The server assembly may also include a stream server forlive video and image streaming and/or a notify server for automaticallytransmitting alert messages between the drones, the user computingdevice, and the server assembly. In this regard, a web service may alsobe dynamically provisioned pending network bandwidth associated with theone or more networks, encryption, and the video and image streaming.

One or more drones of the system may also operate according to one ormore of the following states: a non-operational state defined by beingdocked on the drone dock; a charging state defined by receiving a chargeon the drone dock; an on-duty state when the drone is executing theflight operation; and/or a malfunction state when the drone ismalfunctioned and needs to be repaired.

In other embodiments, a mobile device comprising a software applicationis disclosed with access to any of the herein disclosed drone securitysystems. In this respect, the mobile device may be in communication withthe server assembly and one or more drones and the mobile device mayinclude a non-transitory storage medium, a processor for processing datatransmitted between the server assembly and the drone, and a userinterface for receiving user input and displaying data transmitted fromthe one or more drones.

The software application of the mobile device may include the followingmanagement capabilities: continuously monitoring the location by forminga continuously updated surveillance map and one or more live streams ofthe location; configuring alert message parameters for transmitting oneor more alert messages and recipients of the one or more alert messages;manually and/or automatically selectively viewing the one or more livestreams; deactivating and/or reactivating one or more drones;controlling one or more parameters of the onboard sensors of the droneincluding minimum thresholds for a predetermined alert or pan, zoom,tilt, direction, and frames per second for the imaging device; and/oractivating one or more alarm conditions on one of the onboard sensors orthe imaging device.

Other aspects and features of the present disclosure will becomeapparent to those of ordinary skill in the art, upon reviewing thefollowing detailed description in conjunction with the accompanyingfigures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts a block diagram of an illustrative computing devicearchitecture used in combination with the herein disclosed automateddrone security system, according to an example embodiment.

FIG. 2 depicts an illustration of the automated drone security systemarchitecture according to an example embodiment.

FIG. 3 depicts an illustration of features of the automated dronesecurity system, according to an example embodiment.

FIG. 4 depicts an illustration of drone state transitions during anexemplary mission, according to an example embodiment.

FIG. 5 depicts an illustration of the automated drone security systemdock in a closed state, according to an example embodiment.

FIG. 6 depicts an illustration of the automated drone security systemdock in an open state, according to an example embodiment.

FIG. 7 depicts an exemplary event viewer of an app on a mobile device.

FIG. 8 depicts an exemplary event viewer of an app on a mobile device.

FIG. 9 depicts an exemplary event viewer of an app on a mobile device.

FIG. 10 depicts an exemplary event viewer of an app on a mobile device.

FIG. 11A depicts an exemplary event scheduler of an app on a mobiledevice.

FIG. 11B depicts an exemplary event scheduler of a web-based app.

FIG. 12A depicts an exemplary event viewer of an app on a mobile device.

FIG. 12B depicts an exemplary event viewer of a web-based app.

DESCRIPTION

Throughout this disclosure, certain embodiments are described by way ofexample in relation to designing, operating, and maintaining anautomated drone security system. However, embodiments of the disclosedtechnology are not so limited, and may be applicable to other manuallyoperated and autonomous mechanical craft. Some embodiments of thepresent disclosure will be described more fully hereinafter withreference to the accompanying drawings. This present disclosure may,however, be embodied in many different forms and should not be construedas limited to the embodiments set forth herein.

In the following description, numerous specific details are set forth.However, it is to be understood that embodiments of the presentdisclosure may be practiced without these specific details. In otherinstances, well-known methods, structures, and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription. References to “one embodiment,” “an embodiment,” “exampleembodiment,” “some embodiments,” “certain embodiments,” “variousembodiments,” etc., indicate that the embodiment(s) of the presentdisclosure so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

Throughout the specification and the claims, the following terms take atleast the meanings explicitly associated herein, unless the contextclearly dictates otherwise. The term “or” is intended to mean aninclusive “or.” Further, the terms “a,” “an,” and “the” are intended tomean one or more unless specified otherwise or clear from the context tobe directed to a singular form. Accordingly, “a drone” or “the drone”may refer to one or more drones where applicable.

Unless otherwise specified, the use of the ordinal adjectives “first,”“second,” “third,” etc., to describe a common object, merely indicatethat different instances of like objects are being referred to, and arenot intended to imply that the objects so described must be in a givensequence, either temporally, spatially, in ranking, or in any othermanner.

As used herein, the term “drone” may refer to, or be usedinterchangeably with, “unmanned aerial vehicle” (UAV) or“radio-controlled” (RC) aircraft where appropriate.

In some instances, a computing device may be referred to as a mobiledevice, mobile computing device, a mobile station (MS), terminal,cellular phone, cellular handset, personal digital assistant (PDA),smartphone, wireless phone, organizer, handheld computer, desktopcomputer, laptop computer, tablet computer, tablet, terminal, displaydevice, or some other like terminology. In other instances, a computingdevice may be a processor, controller, or a central processing unit(CPU). In yet other instances, a computing device may be a set ofhardware components.

Various aspects described herein may be implemented using standardprogramming and/or engineering techniques to produce software, firmware,hardware, and/or any combination thereof to control a computing deviceto implement the disclosed subject matter. A computer-readable mediummay include, for example: a magnetic storage device such as a hard disk,a floppy disk or a magnetic strip; an optical storage device such as acompact disk (CD) or digital versatile disk (DVD); a smart card; and aflash memory device such as a card, stick or key drive, or embeddedcomponent. Additionally, it should be appreciated that a carrier wavemay be employed to carry computer-readable electronic data includingthose used in transmitting and receiving electronic data such asstreaming video or in accessing a computer network such as the Internetor a local area network (LAN). Of course, a person of ordinary skill inthe art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of the claimedsubject matter.

System Overview

The present disclosure solution systems, methods, and computer-readablemediums for providing an automated drone security system 200. Accordingto an example embodiment, the system 200 may have one or more of thefollowing features or meet or exceed one or more of the followingrequirements. In certain examples, the system 200 may include videostreaming including video feeds that may be accessed or streamed throughsoftware resident on a computing device (e.g. a mobile app). Thesolution may be operable to provide a user capability of viewing thevideo feed in real-time or with a predetermined delay such as 2 seconds.The predetermined delay may also be adjustable as needed or required.

In a preferred embodiment, the video feed of system 200 may include thefollowing processes: Stream Quarter Video Graphics Array (QVGA) videofrom an onboard computer to a cloud server with limited latency (e.g.less than ˜1 sec latency); relay QVGA video from the cloud server to auser's app on a mobile device with a similar limited latency (e.g. lessthan ˜1 sec latency); stream or upload video in a predetermined format(e.g. High definition) from the onboard computer to the cloud server,wherein the stream, upload, and/or the video format is executed pendingnetwork bandwidth; and/or one-to-many broadcast of HD video from cloudserver with ˜1 sec latency; and/or Encryption.

System 200 may also include executive flight control logic and flightsystem security considerations that include the following processes.High-level executive logic may include state machine with predefinedflight and operation procedures, wherein certain flight and operationprocedures may be triggered by sensor states such as timer, measurementsfrom an inertial measurement unit (IMU), a global positioning system(GPS), velocity, atmospheric conditions, or the like. Flight rangeprediction logic may also be included based on battery/system status andenvironmental conditions. Autonomous RTL logic may also be included forleveraging flight range prediction. Other logic included in system 200may include flight trajectory planner with collision avoidance andcontrol and status communication encryption for security.

System 200 may also include capabilities to coordinate multiple dronesand/or multiple simultaneous flights with overlapping operations ormissions to relay surveillance coverage. Multi-drone relay missions maybe motivated by battery constraints of single drones and may also beinclude capabilities for web-based multiple drone registration with acloud-server-based drone flight coordinator. The cloud-server-baseddrone coordinator may include partial or complete automated coordinationcapabilities. Finally, multi-drone control features of the hereindisclosed system 200 may include capability of relaying multiple dronesfor continuous aerial missions.

The solution 1 may also include environment mapping capabilitiesincluding capabilities for dynamically updating a global map usingflight data, wherein the flight data. Map types may include weather,no-flight zone, flight corridors, ground levels and flight ceilings, orthe like. Map types may also include static obstacles, dynamicobstacles, network connectivity, and/or custom user-specified costfunction map(s).

In certain examples, the herein disclosed system 200 may also includeimage stitching logic comprising processes for two-dimensional and/orthree-dimension processing that forms a map with detected environment,obstacles, or the like that is continuously refined as new images areprocessed. Such data may be transmitted from sensors that are mounted togather real-time images and data that are stitched together in two- tothree-dimensions. For example, a three dimension obstacle map may beincluded with the map for obstacle avoidance, path planning, andintelligent navigation.

The image stitching process may include continuous updated andprocessing of image scans from one or more sensors on the drone toextract one or more features such as environment, obstacles, dock(s),property boundaries, structures, etc. to form the map. As the disclosedsystem 200 continues to received image scans from one or more sensors onthe drone, values associated with the one or more features may beblended with earlier images scans and be updated and/or matched againstearlier image scans to determine whether any changes have occurred thatnecessitate further investigation or action from the system 200.

System 200 may also include one or more basic safety behaviors such asmanual emergency stop (e-stop) for drones. Multiple e-stop behaviorsincluding RTL and/or power cutoff. The one or more basic safetybehaviors may also be operable to wirelessly maintain heartbeatconnectivity with one or multiple drones through 3G/4G, Wifi or RF atall times. In the event that connectivity with the drone is lost orsystem status signals indicate inability to continue mission, the dronemay be operable to autonomously navigate back to the dock. Additionally,the user of the system 200, including an air traffic controller orcoordinator, may react accordingly in order to execute an automatic,partially automatic, and/or manual return of the one or more drones backto the dock. In this respect, the solution 1 of the herein disclosedsystem 200 may include customizable triggers or conditions for e-stop(e.g. a programmed detection of unusual activities).

System 200 may also include network security with operability forencrypted communication for navigation and control signals. The networksecurity may also include operability for encrypted communication forvideo streaming and/or flight sensor data acquisition. Various systems,methods, and computer-readable mediums may also be utilized forproviding the herein disclosed automated drone security system 200, andwill now be described with reference to the accompanying figures.

Front-End System

FIG. 2 depicts an illustration of the automated drone security systemarchitecture according to an example embodiment. According to certainembodiments, security system 200 may comprise a user-facing front-end210 including software, firmware, and/or hardware for monitoring and/orcontrolling a drone 220. In some embodiments, this interface to the usermay comprise a mobile application (“app”) 215 a or other softwareexecutable on a mobile computing device 210 (e.g. a smart phone). Inanother embodiment, the interface may comprise a web-based application215 b accessible through a browser or other software, or a desktopapplication.

In some embodiments, the mobile app 215 a may include a client formanaging one or more locations being secured by drone(s) 220 of system200. A location may be configured with one or more of the followingparameters: geo-fence (e.g., a two- or three-dimensional structuredefining borders of the location); buildings (e.g., polygons withspecified height); obstacles (e.g., polygons with assumed infiniteheight, effectively no-fly zones, etc.); markers (e.g., map markersidentifying points of interest); and/or bases/docks 225 (e.g. mapmarkers identifying locations of drone docks 225).

System 200 may also include several drones 220, wherein each drone 220may be assigned to a specific dock 225, or to multiple docks for dynamicoperations. In some embodiments, additional capabilities of app 215a/215 b or other software may be available dependent on the drone 220 tobe controlled or the characteristics of dock 225, device 210, and/or theassociated server assembly. In an example embodiment, the app 215 a/215b may determine the capabilities of a host device executing the softwareand configure itself accordingly. In another embodiment, the app 215a/215 b may configure itself based on a configuration of the drone 220to be controlled. Alternatively, the software of may come preconfiguredfor a particular host device, a host or target drone that can be definedby the end-user, or for a particular target drone.

In some embodiments, the app 215 a/215 b may provide or supportfunctionality permitting drone 220 and location management. Moreover,the app may provide routine operation setting and scheduling with manualtakeover of drones 220, role management, alerts during manual andautomated control; and/or comment and sharing functionalities.

According to certain embodiments, the app 215 a/215 b may presentinformation about associated drones 220 in a dashboard view. In anexample embodiment, the operational status and/or battery charge of adrone 220 may be displayed and/or other displayable information mayinclude drone destination, position, speed, heading, and altitude.Selecting a drone user interface item may bring up a view with editabledetails and controls to manage status of the drone 220 and assign it toa dock 225 or to execute one or more predetermined operations.

In some embodiments, the app 215 a/215 b may present information aboutcurrently running operations in the dashboard view. In an exampleembodiment, the operations may be grouped by location and/or one or moreindication of each operation item may include a periodically updatedimage from the live video feed associated with the operation. A user mayaccess an operation broadcast view by transmitting input through theuser interface of the app 215 a/215 b (e.g. tapping or clicking-on orotherwise selecting an operation item).

In some embodiments, the user may receive notifications (e.g. alertmessages) indicating the status of one or more current operations. Forexample, when a new operation starts, the user may receive anotification through app 215 a/215 b. Forms of notification include appnotification within the app itself, email, and messaging (e.g., SMS,MMS, etc.). In some embodiments, multiple users may communicate witheach other through a messaging interface of the app 215 a/215 b and/orother software. Through or outside of the messaging interface, users maybe granted permission to view one or more live video feeds andoperational statistics associated with the drones owned or operated byother users. In an example embodiment, a first user may provide a linkto a video feed of drone operation underway to second user. The seconduser may follow the link to launch a live-broadcast interface showing alive view from the associated drone. Operations may be launched from thedashboard of app 215 a/215 b or the like.

In some embodiments, a suitable drone 220 may be selected for anoperation automatically based on one or more operation parameters andstatus of available drones. A drone may also be selected based onfactors such as proximity to one or more predetermined locations,battery status, size of a particular drone for a particular operation,range of the drone, speed of the drone, payload capability of the drone,or other factors.

According to certain embodiments, the interface of the app 215 a/215 bmay also provide a calendar or other scheduling interface for managingone or more operations. For example, FIG. 11A describes an embodiment ofapp 215 a on device 210 depicting an exemplary event scheduler 250 awhereas FIG. 11B similarly depicts app 215 b and an exemplary eventscheduler 250 b. Either event scheduler may schedule operations and mayalso be configured to repeat one or more operations on specifiedintervals during a time period (e.g., every hour from 8 am to 4 pm), onspecific days (e.g., every Monday-Friday), or periodically (e.g. onceevery 4 weeks, every 2 months, etc.). One or more flight pathsassociated with a particular operation may be configured in advance byplacing a plurality of waypoints on one or more maps. Components of thesystem 200, including app 215 a/215 b, may ensure that the flight pathdoes not exceed a certain maximum duration, range, or other performanceparameter, for example, a “safe” drone flight time. Users may also beable to view a list of recordings arranged by time and date. In someembodiments, the scheduling interface may include search functionalityto improve ease of use as well as facilitating repeatability of one ormore previously executed operations.

According to certain embodiments, the app 215 a or 215 b may include aplayback interface for viewing captured video and other recorded data.For example, FIG. 12A describes an embodiment of app 215 a on device 210depicting an exemplary event viewer 240 a whereas FIG. 12B similarlydepicts app 215 b and an exemplary event viewer 240 b. This isparticularly useful where a particular structure or object can bemonitored to mitigate damage or losses associated with accidents as seenin FIG. 12B where a structure is on fire. In this instance, users may beable to immediately respond or the system 200 may be configured toautomatically detect episodes as in FIG. 12B and coordinate withappropriate response personnel. The playback interface of each viewer240 a and 240 b may be similar to a live-broadcast interface, however,the user may be able to control the playback position in the former.

Users may also be capable of appending a description, a title, or othernotes to the recordings. Users may also be able to utilize viewers 240 aand 240 b in combination with one or more maps and such appendedinformation may be viewable as part of the list of recordings. Inanother embodiment, the app may launch or trigger another application onthe host device for viewing content. A user may also share recordingswith other users through the app 215 a and 215 b. In some embodiments, auser may be able to tag and share only desired portions of recordingssuch as clips of interest.

Additionally, in regards to live viewing, as seen in FIGS. 7-10 whichdepict exemplary live or previous event viewers 240 a, app 215 a ondevice 210 that may include different controls and indicators for system200 and corresponding end-users. For example, in FIG. 7, viewer 240 a isshown displaying information related to an event entitled, “LakeLagunita”, wherein one or more alerts have been defined with informationrelated to an “alert event” that earlier took place at a predeterminedlocation, “West Building Entrance”. Information may be compiledassociated with the event of FIG. 7 including a combination of videos,photos, location, and the like. Similarly, FIG. 8 depicts informationrelated to the vent of FIG. 7 as seen in app 215 a of device 210 withinformation related to a plurality of locations associated with thelocation of FIG. 7, including nest 225, one or more markers associatedwith the location, building, a perimeter of the location, and theability for system 200 to dispatch one or more drones 220 to execute apath, go to a location, or carry out one or more operations.

Similarly, FIG. 9 depicts a view one or more maps in app 215 a that showlive video feeds as well as path of one or more drones 220 of system200. In this respect, a user may select which drone 220 to operate,which operation to execute as well as access information related tooperational status, position, path, battery, or the like. Similarly, asseen in FIG. 10, app 215 a may be capable of imparting image and/orvideo control to end-users. For example, through the app 215 a a usermay manually or the system 200 may automatically control camera tilt,heading and/or pinch for cameras of drone 220 between a plurality oforientations and positions.

Back-End Architecture

According to certain embodiments, the drone security system 200 maycomprise a back-end including one or more servers 240. A server 240 mayperform various functions including collision mapping, dronecoordination and air traffic control as well as storage/processing ofcaptured images and video streams. In one example embodiment, theback-end architecture may comprise, or be in communication with, one ormore of a database server, web server, drone coordination relay, streamserver, notify server, and/or a scheduler. In some embodiments, thisfunctionality may be split between multiple servers, which may beprovided by one or more discrete providers. In an example embodiment, aweb service for hosting computer applications or other cloud computingresource may be dynamically provisioned to match demand and ensurequality of service of the drone security system 200. For example, thedrone security system 200 may be compatible with the Amazon EC2 cloudcomputing platform.

Database Server

According to certain embodiments, the above-described database servermay store master data, telemetry information, and mission data as wellas logging and trace information. Software of the database server may bebased on the object-relational database system PostgresSQL the databaseserver is not so limited other approaches may be used as needed orrequired. This database system is not limited to only organizing andstoring data and instead, it may be also used to eliminate a need ofhaving an application server (e.g. 2nd Layer). In some embodiments,almost every functional requirement may be realized by using thedatabase's programming language, PL/pgSQL. The database may also providean API to the web server for data interchange based on JSONspecifications. In some embodiments, the database may also directlyinteract with the described drone coordination relay to control andtrack one or more drones 220.

According to certain embodiments, the database server may be optimallydesigned for storing large amounts of data, responding quickly toincoming requests, having a high availability and historizing masterdata. In an example embodiment, the database server may store tenmegabytes of raw data (e.g. data related to telemetry and tracking), aswell as 200 megabytes of video material (e.g. per drone 220). To handlethis amount of data, a sophisticated combination of table partitioning,table inheritance as well as database clustering may be implemented tofulfill these requirements.

Mission Control Module

According to certain embodiments, the mission control module may be partof the database backend. FIG. 4 depicts an illustration of drone statetransitions during an exemplary mission, according to an exampleembodiment. The states marked with triangles, including drone states anduser command states, are handled by the Mission Control Module. In someembodiments, the mission control module may perform one or more oftriggering one or more scheduled missions, dispatching a drone 220 on amission, ordering control of operations, status tracking of a drone 220during missions, accepting and delivering operator instructions,finalizing and archiving missions and mission data, as well as ensuringoperation safety as the drone 220, other drones 220, and other staticand dynamic objects.

This module may directly interact with the drone coordination relayand/or drone navigator process and may also control these componentsbased on mission-specific requirements, sensor data, drone states, statetransitions, or the like. The mission control module may also handlestates like low battery, failover in case of unresponsive backendhardware and malfunctions indicated by the drone 220 itself. In someembodiments, this module may include logic for collision avoidance.

Web Server

In an example embodiment, the web server may be a standard componentbased on Apache Web Server and PHP or the like. For availability andperformance reasons the load may be balanced across multiple nodes.

Drone Coordination Relay

According to certain embodiments, the drone coordination relay maydirectly interact with the database server. For example, if a mission isscheduled, manually or automatically, the database server may cause thedrone coordination relay to dispatch a mission at drone coordination andfork a drone navigator process. This process may run independently fromthe drone coordination relay and/or take over the following tasks,including, reading the status from the drone periodically (e.g., everytwo seconds) and write the status to the database backend. The periodicreading may be customizable so that reading is done more quickly or moreslowly depending on bandwidth, storage capabilities, or user preference.The database may also return with the next instruction to proceed (e.g.,a next waypoint to approach).

When an instruction is given by the database backend, the dronenavigator process may contact the drone coordination to initiate thedesired action. This action may be, for example, to fly to a newdestination, to fly a pattern at the current position, or to tilt thecamera. If the database backend indicates that the last waypoint hasbeen reached, then the drone navigator process may initiate areturn-to-landing procedure. After the drone has landed and switchedback to an “idle” state, the process may finish. When a mission startsagain the drone coordination relay may fork a drone navigator processand/or also a streaming server process. In some embodiments, the dronecoordination relay may be programmed using Shell Scripting Language.

Stream Server

According to certain embodiments, the Streaming Server Process mayreceive the video from one or more cameras of the drone and multiplex itto connected consumers. Additionally, the Streaming Server Process maytake periodic snapshots of the video and store the video on disk. If amission has ended, the Streaming Server Process may archive the videoand register the file in the database. Afterwards the Streaming ServerProcess may end.

Notify Server

According to certain embodiments, the Notify Server may sendnotifications to the user including instant messages within the app, SMSmessages, and/or emails to user devices like mobile phones, tablets,laptops, personal computers and other computing devices. If apredetermined condition is recognized at the database backend (e.g. apredetermined level in a battery of the drone or sensory level from anonboard infrared sensor indicating a change in environment of a locationbe surveilled), an instant message may be triggered and delivered by theNotify Server.

Scheduler

According to certain embodiments, the Scheduler may automatically startand reschedule repetitive missions. The scheduler may also observe thestatus of drones currently not airborne and execute the pending backlogof the Drone Coordination Relay. Moreover, the scheduler may initiatedaily maintenance operations on the database and the operating system.In some embodiments, daily maintenance on the database may include oneor more the following tasks: 1. Reorganizing tables; 2. Computing tablestatistics for better performance; 3. Truncating outdated protocol data;4. Creating new partitions; and/or 5. Backing-up of the database.

Drone Architecture

According to certain embodiments, the drone security system 200 mayinclude, or be configured to operate with, one or more drones 220. Insome embodiments, the drone security system 200 may be compatible withmultiple drones 220 of various makes, models, and capabilities.

An exemplary drone 220 useable with the drone security system 200 maymeet one or more of the following criteria: 1. Flight time/range: afully charged drone 220 may be able to fly for 10-30 minutes dependingon drone type; 2. Loiter time: drone loiter time at each waypoint may beindependently configurable; 3. Camera focus, tilt, and zoom control:camera may be controlled via app; 4. Safety systems: deployableparachute, radio-based self-position broadcast, emergency landingsystem, and e-stop functionality; and/or 5. System redundancy:drivetrain hardware, communication hardware, onboard computationhardware, and onboard sensors (e.g. IMU, GPS) may have backups or beable to perform in a reduced capacity.

In some embodiments, a drone 220 may also support wireless, mobile,and/or satellite network connections. For example, a drone 220 maycommunicate telemetry and video data via LTE connection. Encryption orother technology may also be used to secure communications to and fromdrone 220.

In some embodiments, the drone 220 may include one or more multiplesensor devices such as a camera or other image capture device, aninfrared sensor, Optical, multi-spectral, hyperspectral, laser, andoptical SAR technologies, gas sensors, or the like mounted thereon. Inthose embodiments where drone 220 is equipped with a camera, the cameramay be permanently affixed or removably attached. The camera may captureimages and/or video of the drone 220's surroundings. In someembodiments, the captured video or images may be streamed live from thedrone 220 through the backend to the app. In another embodiment, thecontent may be streamed from the drone 220 to the Copilot or devicehosting the app software, or to the Copilot and then to the app overanother network or connection. In another embodiment, the drone 220 maysave video locally to an on-board memory or other storage and/orremotely save captured content to an external storage medium. Thecaptured content may later be retrieved from the drone 220, the externalstorage medium, or the like, for example, after landing in a nest, orother docking station.

In some embodiments, the drone 220 may be able to automatically changethe resolution, frame rate, or other quality of video or images beingcaptured. For example, a drone 220 may typically capture video at afirst resolution for streaming or local recording. When an area ofinterest appears or a particular event or condition is satisfied, thedrone 220 may switch to capturing video at a higher resolution. Thischange in quality may be triggered manually by the user, or occurautomatically in response to an event. For example, higher qualitycapture may be activated responsive to detection of activity by one ormore sensors such as a sudden change in temperature or ambient noiselevel that can cause a drone 220 to change a quality of capture.

In some embodiments, the drone 220 may be equipped with a variety ofadditional sensors, including but not limited to, accelerometers,gyroscopes, altimeters, barometers, microphones, temperature sensors,thermal optics, and location sensors. Data provided by some or allsensors of drone 220 may be transmitted back to a front-end or back-endcomputing device for presentation to a user and/or processing/storage.According to certain embodiments, a drone 220 may operate according toone or more of the following states: in storage (e.g. drone 220 has notbeen assigned to a base, non-operational); charging (e.g. drone 220 isassigned to a base and is docked and charging); on duty (e.g. a drone220 is currently flying a mission); malfunction (drone 220 hasmalfunctioned and needs to be repaired); and in repair (drone 220 hasbeen unassigned from its base and is being serviced).

According to certain embodiments, a drone 220 may also engage in one ormore of the following operations: manual (e.g. a user manuallydispatches a drone 220 to a specified coordinate using the app); alarm(a drone 220 is automatically dispatched to where an alarm wastriggered); and scheduled (e.g. routine drone 220 flights are dispatchedautomatically in predefined intervals).

In some embodiments, a user may launch a manual operation as well asassume manual control of ongoing alarm and scheduled operations. Duringmanual operation, only a single user may have manual control of anoperation. In an example embodiment, only the current operator maydismiss, end, edit, and/or suspend a manually controlled operation. Insome embodiments, an operator may prompt another user to assume manualcontrol or assign manual control to another user. In another embodiment,a user with sufficient privileges may override a current operator andassume manual control themselves without permission.

During manual operation, a user may send a drone 220 to a plurality ofcoordinates by interacting with the map, as well as controlling thecamera pan, tilt, and zoom using gestures, a mouse, or other inputdevice. After dismissal or completion of an operation, the drone 220 mayautonomously return to its dock or base or another predeterminedposition. In some embodiments, an operation may be automaticallydismissed if one or more predetermined conditions are satisfied such asthe battery charge of a drone 220 being low, or the drone 220 isotherwise forced to retire. An operation may also be assumed by seconddrone 220 when a first drone 220 is forced to retire. This relay may beperformed with minimal or no interruption to drone broadcast.

In some embodiments, drone takeoff and/or landing may be handledautonomously by the drone coordination server. Alternatively, a drone220 may be at least partially under manual control during thesesequences.

Copilot and Autopilot

According to certain embodiments, the drone security system 200 maycomprise a “Copilot” for assisting with drone management. The Copilotmay include software, firmware, and/or hardware external from a drone220 and configured to receive telemetry data from the drone 220. In anexample embodiment, the copilot may comprise proprietary communicationand drone management software at least partially running or resident ona computing device. For example, the copilot may run on a Raspberry Pior other system on a chip (SOC). Alternatively, the Copilot may comprisea combination of different single-board computers.

In some embodiments, the Copilot may receive user commands from the appor other user software. The Copilot may be linked to the DroneCoordination Relay by ROS and/or HTTP/REST. The Copilot may communicatewith an Autopilot system for remotely piloting an aircraft that is outof sight. In an example embodiment, the Autopilot system may comprise anopen-source autopilot system oriented toward autonomous aircraft.

Access Control

According to certain embodiments, the system 200 may include accesscontrol functionality, wherein access to drone functionality may belimited on a per-user(s) and/or per-location(s) basis. Permissions maydefine which functionality is available to a user. A role may be asystem-wide group or class of permissions and a user may be granted adifferent role for each location.

Drone Dock

According to certain embodiments, the drone security system 200 maycomprise a docking station or other platform 225 for storing andlanding/launching drones 220. For example, FIG. 5 depicts anillustration of the automated drone security system dock in a closedstate, according to an example embodiment. FIG. 6 depicts anillustration of the automated drone security system dock in an openstate, according to an example embodiment.

Such a dock 225 may be referred to herein as a “nest.” In someembodiments, the dock 225 may serve as a housing for the drone 220, andmay be located on rooftops, cars, in a backyard, or elsewhere. The dock225 may protect the drone 220 from the elements while it recharges orawaits an operation. Once a dock 225 is installed, the drone 220 fleetmay be operated remotely, so that there is no need to manually accessthe dock 225 during routine operation.

In some embodiments, a drone 220 may charge while docked. In an exampleembodiment, a nest may supply a minimum of 12 volts at 10 amps for fastcharging. The dock 225 may be connected to an external power grid, orreceive power from alternative sources such as solar, wind, and/orthermal and/or store this power in an external power supply such as oneor more batteries. In certain embodiments, the external power supply ofthe dock 225 may be one or more backup batteries so that the dock 225may still open/close or even continue to charge drones 220 during apower outage, overcast weather, and/or other disruptions to the powersupply.

In some embodiments, a drone 220 may be charged through induction orthrough contact with conductive receivers on the dock 225 and the bodyof the drone 220. In an example embodiment, the conductive receivers maybe conductive pads on the legs and/or feet of a drone 220 that contactcharging terminals on a floor or landing pad of the dock 225. In someembodiments, a drone 220 may be “hot charged” such that drone 220 downtime or unavailability in between or during operations may be minimized.

In some embodiments, the dock 225 may maintain a network connectionthrough a wired (Ethernet) or wireless connection (e.g., WiFi, 3G, 4G,LTE, etc.). The dock 225 may also report dock status, including whetherthe dock 225 is open or closed, empty or occupied, charging a drone 220or not, receiving external power, the location of the dock 225, a levelof charge of one or more backup batteries, maintenance alerts, or othersensor data related to the dock 225. In another embodiment, the dock 225may also share its network connection with a docked drone 220, or assumeresponsibility for reporting drone status in addition to or in place ofthe drone 220.

In some embodiments, the dock 225 may be equipped with one or morecameras. Accordingly, the dock 225 may also provide a live video feed ortwo-dimensional and/or three-dimensional images of its surroundings. Thedock 225 may also be equipped with various sensors and in yet anotherembodiment, the dock 225 may be equipped with radar or otherobject-detection systems.

In some embodiments, the dock 225 may provide autonomous landingguidance. For example, differential GPS data detected onboard (e.g., RTKGPS) may be used to automatically or partially automatically guide adrone within range of optical recognition. Once the drone 220 is inrange, cameras or other image capture devices may be used to recognizelights or other identifiers on the drone 220. In an example embodiment,there may be multiple mono and/or stereo cameras on the landing pad ofthe dock 225. The drone 220 may be outfitted with focused LED lights incustom patterns and lighting up in sequence. Redundant visual sensorplacements and LED arrays/reflectors on the drone 220 may be tuned insuch a way that an LED array/reflector is always visible to one of theoptical sensors on dock 225, even if the lighting conditions are lessthan ideal if, for example, the sun lies directly in the line of sightof one or more of the visual sensors.

Additionally polarized filters may be employed, so that the camerarecognizes the LED arrays/reflectors even with conflicting sources oflight. A strobing pattern or other predetermined pattern may help theprocessor of the dock 225 identify the orientation and approximatedistance of the drone 220. Accordingly, the dock 225 may visually verifythat the correct drone 220 is in appropriate position to dock 225. Animaging algorithm may be used in conjunction with telemetry to establisha landing trajectory, which may then be communicated to the drone 220.

In some embodiments, the dock 225 may be secured to prevent physicaland/or electronic tampering. For example, a locking mechanism may keepthe dock 225 sealed when a drone 220 is not preparing to launch or landin the dock 225. Moreover, electronic access to the dock 225 may belimited through access control as described herein or the like. In anexample embodiment, intrusion or tampering may be detected automaticallyso that a response can be triggered (e.g. setting of an alarm). Thealarm may include emitting an audible siren or other indication ofemergency. The alarm may also include notifying an owner or operator ofthe dock 225 by the app, textual message, or other electronic means. Insome embodiments, dock 225s expected to be placed in high-risk areas maybe hardened or contain additional features to prevent intrusion orweather damage.

Certain embodiments of the present disclosure are described above withreference to block and flow diagrams of systems and methods and/orcomputer program products according to example embodiments of thepresent disclosure. It will be understood that one or more blocks of theblock diagrams and flow diagrams, and combinations of blocks in theblock diagrams and flow diagrams, respectively, may be implemented bycomputer-executable program instructions. Likewise, some blocks of theblock diagrams and flow diagrams may not necessarily need to beperformed in the order presented, or may not necessarily need to beperformed at all, according to some embodiments of the presentdisclosure.

These computer-executable program instructions may be loaded onto ageneral-purpose computer, a special-purpose computer, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meansthat implement one or more functions specified in the flow diagram blockor blocks.

As an example, embodiments of the present disclosure may provide for acomputer program product, comprising a computer-usable medium having acomputer-readable program code or program instructions embodied therein,said computer-readable program code adapted to be executed to implementone or more functions specified in the flow diagram block or blocks. Thecomputer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational elements or steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide elements or steps for implementing the functionsspecified in the flow diagram block or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specified functionsand program instruction means for performing the specified functions. Itwill also be understood that each block of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, may be implemented by special-purpose, hardware-based computersystems that perform the specified functions, elements or steps, orcombinations of special-purpose hardware and computer instructions.

While certain embodiments of the present disclosure have been describedin connection with what is presently considered to be the most practicaland various embodiments, it is to be understood that the presentdisclosure is not to be limited to the disclosed embodiments, but on thecontrary, is intended to cover various modifications and equivalentarrangements included within the scope of the appended claims. Althoughspecific terms are employed herein, they are used in a generic anddescriptive sense only and not for purposes of limitation.

This written description uses examples to disclose certain embodimentsof the present disclosure, including the best mode, and also to enableany person skilled in the art to practice certain embodiments of thepresent disclosure, including making and using any devices or systemsand performing any incorporated methods. The patentable scope of certainembodiments of the present disclosure is defined in the claims, and mayinclude other examples that occur to those skilled in the art. Suchother examples are intended to be within the scope of the claims if theyhave structural elements that do not differ from the literal language ofthe claims, or if they include equivalent structural elements withinsubstantial differences from the literal language of the claims.

What is claimed is:
 1. A security system for surveilling a location,comprising: a plurality of drones, each of the plurality of dronescomprising: one or more onboard sensors; and an imaging device formeasuring surveillance data, wherein the surveillance data comprisesimages and telemetry data of the location, the location is selected fromthe group consisting of one or more structures, buildings, and parcelsof land, and each drone being capable of: executing a flight operationfor surveilling the location for a period of time, storing andtransmitting the surveillance data to a server assembly, the serverassembly coordinating the plurality of drone and receiving thesurveillance data measured from the plurality of drone, detecting one ormore alarm conditions using the one of the onboard sensors of one ormore of the plurality of drones, the one or more alarm conditionsincluding intrusion, theft, burglary, break-in or tampering of thelocation, being dispatched with one or more of the drones to an event ofinterest at the location being surveilled based on detecting the one ormore alarm conditions, deactivating and/or reactivating one or more ofthe plurality of drones, controlling parameters of the one or moreonboard sensors including minimum thresholds for a predetermined alertor pan, zoom, tilt, direction, and frames per second for the imagingdevice, and in response to the controlling, activating a function on oneof the one or more onboard sensors or the imaging device based on theone or more alarm detected conditions, and a plurality of drone docksoperable for drone launching, landing, and storing the plurality ofdrones; and a user computing device in communication with the serverassembly and the plurality of drones, the user computing device having anon-transitory storage medium, a processor for processing thesurveillance data between the server assembly and the plurality ofdrones, and a user interface for receiving user input and displaying thesurveillance data from the plurality of drones; wherein the flightoperation is automatically and/or manually controlled by the usercomputing device or the server assembly in connection with the locationfor uninterrupted aerial coverage of the event of interest.
 2. Thesystem of claim 1, wherein a battery of each of the plurality of dronesis charged by each of the plurality of the drone docks through aconduction pad or through an inductive charging device.
 3. The system ofclaim 2, wherein when the battery of the each of the plurality of droneshas a minimum charge, the drone is automatically returned to each of theplurality of the drone docks for charging.
 4. The system of claim 2, thesystem further comprising flight and security control logic comprising:executive logic defined by one or more predefined flight and operationprocedures triggered by sensor states associated with the one or moreonboard sensors of each of the plurality of drones including velocity, atimer, an inertial measurement unit, and a global positioning system(GPS); flight range prediction logic defined by a status of the batteryof each of the plurality of drones and environmental conditionsincluding wind speed and direction, humidity, altitude, temperature, andair pressure, and a flight trajectory planner associated with one ormore flight operations; and autonomous logic associated with the flightrange prediction logic including collision avoidance logic and controland encryption for information transmitted between each of the pluralityof drones, the server assembly and the user computing device.
 5. Thesystem of claim 4, the collision avoidance logic including a detect andtrack module associated with static and dynamic structures and obstaclesdefined by a predetermined location, a predetermined flight path, and/orstatic and dynamic structures and obstacles sensed by the one or moreonboard sensors of each of the plurality of drones.
 6. The system ofclaim 2, wherein the plurality of drones operate according to one ormore of the following states: a non-operational state defined by beingdocked on the plurality of drone docks; a charging state defined byreceiving a charge on the plurality of drone docks; an on-duty statewhen one of the plurality of drones is executing the flight operation;and a malfunction state when one of the plurality of drones ismalfunctioned and needs to be repaired.
 7. The system of claim 1, thesystem further comprising a video feed system comprising one or moremethods of: streaming quarter video graphics array (QVGA) video from anonboard computing system of each of the plurality of drones to a cloudserver associated with the server assembly with a predetermined latency;relaying QVGA video from the cloud server to the user computing devicewith the predetermined latency; and streaming or uploading video in apredetermined format from the onboard computing system of each of theplurality of drones to the cloud server, wherein the predeterminedformat is determined pending network bandwidth and encryption.
 8. Thesystem of claim 1, the system further comprising a process comprising:forming or monitoring a continuously-updated two-dimensional and/orthree-dimensional map of the location with image stitching logic definedby two- and/or three-dimensional blending of previously and liverecorded two- and/or three-dimension data gathered from the one or moreonboard sensors and imaging devices of each of the plurality of drones.9. The system of claim 1, wherein one or more of the plurality of dronesof the system maintain connectivity with the server assembly or the usercomputing device through 3G/4G, RF, and/or a local wireless network. 10.The system of claim 1, wherein one or more of the plurality of drones orthe user computing device is automatically dispatched to a location ofinterest based on data detected from onboard sensors of the one or moreof the plurality of drones, alert messages are automatically configuredbased on one or more predetermined detected parameters of the locationor one or more of the plurality of drones, and causes alert messages tobe manually or automatically transmitted to the user computing device orother user computing devices securely connected therewith.
 11. Thesystem of claim 1, wherein the plurality of drone docks positioned on orthroughout the location, wherein each of the plurality of drones iscapable of being housed, landing upon, or receiving a charge to itsbattery in connection with any one of the plurality of drone docks,wherein each drone dock is wirelessly connectable to the server assemblyand the user computing device to store and transmit data from one ormore of the plurality of drones docked thereon.
 12. The system of claim1, the user computing device further comprising an event schedulingmanager for manually or automatically selecting one of the drones toexecute one of a plurality of flight operations.
 13. The system of claim1, the user computing device further comprising an event viewer for liveviewing the flight operation being executed by the plurality of dronesof the system and for viewing previously captured data by the pluralityof drones of the system.
 14. The system of claim 1, wherein the userinterface displays operational status of the plurality of drones. 15.The system of claim 1, wherein the server assembly comprises: a databaseserver operatively connected to one or more web servers across one ormore networks, each server operable to permanently store andcontinuously update a database of master surveillance data, telemetryinformation, mission data, collision mapping, drone coordination, airtraffic control, captured images, and video streams; a stream server forlive video and image streaming; and a notify server for automaticallytransmitting alert messages between the plurality of drones, the usercomputing device, and the server assembly; wherein a web service isdynamically provisioned pending network bandwidth associated with theone or more networks, encryption, and the video and image streaming. 16.A mobile device with access to an automated drone security system,wherein the automated drone security system comprising: a plurality ofdrones, each of the plurality of drones comprising: one or more onboardsensors; and an imaging device for measuring surveillance data, whereinthe surveillance data comprises images and telemetry data of thelocation, the location is selected from the group consisting of one ormore structures, buildings, and parcels of land, and each drone beingcapable of: executing a flight operation for surveilling the locationfor a period of time, storing and transmitting the surveillance data toa server assembly, the server assembly coordinating the plurality ofdrone and receiving the surveillance data measured from the plurality ofdrone, detecting one or more alarm conditions using the one of theonboard sensors of one or more of the plurality of drones, the one ormore alarm conditions including intrusion, theft, burglary, break-in ortampering of the location, being dispatched with one or more of thedrones to an event of interest at the location being surveilled based ondetecting the one or more alarm conditions, deactivating and/orreactivating one or more of the plurality of drones, controllingparameters of the one or more onboard sensors including minimumthresholds for a predetermined alert or pan, zoom, tilt, direction, andframes per second for the imaging device, and in response to thecontrolling, activating a function on one of the one or more onboardsensors or the imaging device based on the one or more alarm detectedconditions, and a plurality of drone docks operable for drone launching,landing, and storing the plurality of drones, wherein the mobile deviceis in communication with the server assembly and the plurality ofdrones, the mobile device having a non-transitory storage medium, aprocessor for processing the surveillance data between the serverassembly and the plurality of drones, and a user interface for receivinguser input and displaying the surveillance data from the plurality ofdrones, wherein the flight operation is automatically and/or manuallycontrolled by the user computing device or the server assembly inconnection with the location for uninterrupted aerial coverage of theevent of interest.
 17. The mobile device of claim 16, wherein theprocessor: continuously monitoring the location by forming acontinuously updated surveillance map and one or more live streams ofthe location; configuring alert message parameters for transmitting oneor more alert messages and recipients of the one or more alert messages;and selectively viewing the one or more live streams.
 18. The mobiledevice of claim 16, wherein the server assembly further comprisingflight and security control logic comprising one or more of: executivelogic defined by one or more predefined flight and operation procedurestriggered by sensor states associated with the one or more onboardsensors of each of the plurality of drones including velocity, a timer,an inertial measurement unit, and a global positioning system (GPS);flight range prediction logic defined by a status of the battery of eachof the plurality of the drones and environmental conditions includingwind speed and direction, humidity, altitude, temperature, and airpressure, and a flight trajectory planner associated with one or moreflight operations; and autonomous logic associated with the flight rangeprediction logic including collision avoidance logic and control andencryption for information transmitted between each of the plurality ofdrones, the server assembly and the mobile device.
 19. The mobile deviceof claim 16, wherein a continuously-updated two-dimensional andthree-dimensional map is formed on the user interface of the mobiledevice of the location with image stitching logic defined by two- and/orthree-dimensional blending of previously and live recorded two- and/orthree-dimension data gathered from the one or more onboard sensors andimaging devices of each of the plurality of drones.